Modulation, coding and redundancy version in a wireless network

ABSTRACT

A wireless device receives a first downlink control information (DCI) indicating first uplink resources of a licensed cell. The first DCI comprising a first field indicating one of: a modulation and coding scheme (MCS) for an initial transmission or a re-transmission redundancy version (RV). The wireless device receives a second DCI indicating second uplink resources of a licensed-assisted-access cell. The second DCI comprises an MCS field and an RV field. The wireless device transmits a first transport block (TB) employing the first field and transmits a second TB employing the MCS field and the RV field.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/309,885, filed Mar. 17, 2016, and U.S. Provisional Application62/313,009, filed Mar. 24, 2016, which are hereby incorporated byreference in their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is an example diagram depicting OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 4 is an example block diagram of a base station and a wirelessdevice as per an aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10 is an example diagram depicting a downlink burst as per anaspect of an embodiment of the present disclosure.

FIG. 11 is an example diagram depicting a plurality of cells as per anaspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting listen before talk procedures asper an aspect of an embodiment of the present disclosure.

FIG. 13A and FIG. 13B are an example diagrams depicting a plurality ofcells as per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram depicting transport block transmissionsusing HARQ as per an aspect of an embodiment of the present disclosure.

FIG. 15 is an example diagram depicting example DCI fields as per anaspect of an embodiment of the present disclosure.

FIG. 16 is an example DCI fields as per an aspect of an embodiment ofthe present disclosure.

FIG. 17 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 18 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 19 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 20 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 21 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 22 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 23 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

FIG. 24 is an example flow diagram illustrating an aspect of anembodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofcarrier aggregation. Embodiments of the technology disclosed herein maybe employed in the technical field of multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LAA licensed assisted access

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, the radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as 0.5 msec, 1 msec,2 msec, and 5 msec may also be supported. Subframe(s) may consist of twoor more slots (for example, slots 206 and 207). For the example of FDD,10 subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in each 10 ms interval. Uplinkand downlink transmissions may be separated in the frequency domain.Slot(s) may include a plurality of OFDM symbols 203. The number of OFDMsymbols 203 in a slot 206 may depend on the cyclic prefix length andsubcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for each antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to aspects of an embodiments, transceiver(s) may be employed.A transceiver is a device that includes both a transmitter and receiver.Transceivers may be employed in devices such as wireless devices, basestations, relay nodes, and/or the like. Example embodiments for radiotechnology implemented in communication interface 402, 407 and wirelesslink 411 are illustrated are FIG. 1, FIG. 2, FIG. 3, FIG. 5, andassociated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to various aspects of an embodiment, an LTE network mayinclude a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (for example, interconnected employing an X2interface). Base stations may also be connected employing, for example,an S1 interface to an EPC. For example, base stations may beinterconnected to the MME employing the S1-MME interface and to the S-G)employing the S1-U interface. The S1 interface may support amany-to-many relation between MMEs/Serving Gateways and base stations. Abase station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink,the carrier corresponding to the PCell may be the Uplink PrimaryComponent Carrier (UL PCC). Depending on wireless device capabilities,Secondary Cells (SCells) may be configured to form together with thePCell a set of serving cells. In the downlink, the carrier correspondingto an SCell may be a Downlink Secondary Component Carrier (DL SCC),while in the uplink, it may be an Uplink Secondary Component Carrier (ULSCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may apply,for example, to carrier activation. When the specification indicatesthat a first carrier is activated, the specification may also mean thatthe cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present disclosure.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC_CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the disclosure.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise two subsets: the Master CellGroup (MCG) containing the serving cells of the MeNB, and the SecondaryCell Group (SCG) containing the serving cells of the SeNB. For a SCG,one or more of the following may be applied. At least one cell in theSCG may have a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), may be configured with PUCCHresources. When the SCG is configured, there may be at least one SCGbearer or one Split bearer. Upon detection of a physical layer problemor a random access problem on a PSCell, or the maximum number of RLCretransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG may be stopped, anda MeNB may be informed by the UE of a SCG failure type. For splitbearer, the DL data transfer over the MeNB may be maintained. The RLC AMbearer may be configured for the split bearer. Like a PCell, a PSCellmay not be de-activated. A PSCell may be changed with a SCG change (forexample, with a security key change and a RACH procedure), and/orneither a direct bearer type change between a Split bearer and a SCGbearer nor simultaneous configuration of a SCG and a Split bearer may besupported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied. The MeNB may maintain theRRM measurement configuration of the UE and may, (for example, based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE. Upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so).For UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB. The MeNB and the SeNBmay exchange information about a UE configuration by employing RRCcontainers (inter-node messages) carried in X2 messages. The SeNB mayinitiate a reconfiguration of its existing serving cells (for example, aPUCCH towards the SeNB). The SeNB may decide which cell is the PSCellwithin the SCG. The MeNB may not change the content of the RRCconfiguration provided by the SeNB. In the case of a SCG addition and aSCG SCell addition, the MeNB may provide the latest measurement resultsfor the SCG cell(s). Both a MeNB and a SeNB may know the SFN andsubframe offset of each other by OAM, (for example, for the purpose ofDRX alignment and identification of a measurement gap). In an example,when adding a new SCG SCell, dedicated RRC signaling may be used forsending required system information of the cell as for CA, except forthe SFN acquired from a MIB of the PSCell of a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprises aPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG includes SCell2 and SCell3,and sTAG2 comprises SCell4. Up to four TAGs may be supported in a cellgroup (MCG or SCG) and other example TAG configurations may also beprovided. In various examples in this disclosure, example mechanisms aredescribed for a pTAG and an sTAG. Some of the example mechanisms may beapplied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to an embodiment, initial timing alignment may be achievedthrough a random access procedure. This may involve a UE transmitting arandom access preamble and an eNB responding with an initial TA commandNTA (amount of timing advance) within a random access response window.The start of the random access preamble may be aligned with the start ofa corresponding uplink subframe at the UE assuming NTA=0. The eNB mayestimate the uplink timing from the random access preamble transmittedby the UE. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The UE may determine the initial uplink transmissiontiming relative to the corresponding downlink of the sTAG on which thepreamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to variousaspects of an embodiment, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding (configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, (for example, at least one RRC reconfigurationmessage), may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of thepTAG. When an SCell is added/configured without a TAG index, the SCellmay be explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (for example, to establish, modify and/orrelease RBs, to perform handover, to setup, modify, and/or releasemeasurements, to add, modify, and/or release SCells). If the receivedRRC Connection Reconfiguration message includes the sCellToReleaseList,the UE may perform an SCell release. If the received RRC ConnectionReconfiguration message includes the sCellToAddModList, the UE mayperform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH may only be transmitted onthe PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. This mayrequire not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum may therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it may be beneficialthat more spectrum be made available for deploying macro cells as wellas small cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, may be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA may offer an alternative for operators to make use ofunlicensed spectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAmay utilize at least energy detection to determine the presence orabsence of other signals on a channel in order to determine if a channelis occupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by UEs, time & frequency synchronizationof UEs, and/or the like.

In an example embodiment, a DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the eNBtransmissions can start only at the subframe boundary. LAA may supporttransmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

An LBT procedure may be employed for fair and friendly coexistence ofLAA with other operators and technologies operating in an unlicensedspectrum. LBT procedures on a node attempting to transmit on a carrierin an unlicensed spectrum may require the node to perform a clearchannel assessment to determine if the channel is free for use. An LBTprocedure may involve at least energy detection to determine if thechannel is being used. For example, regulatory requirements in someregions, for example, in Europe, may specify an energy detectionthreshold such that if a node receives energy greater than thisthreshold, the node assumes that the channel is not free. While nodesmay follow such regulatory requirements, a node may optionally use alower threshold for energy detection than that specified by regulatoryrequirements. In an example, LAA may employ a mechanism to adaptivelychange the energy detection threshold. For example, LAA may employ amechanism to adaptively lower the energy detection threshold from anupper bound. Adaptation mechanism(s) may not preclude static orsemi-static setting of the threshold. In an example a Category 4 LBTmechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies, no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (for example, LBT withoutrandom back-off) may be implemented. The duration of time that thechannel is sensed to be idle before the transmitting entity transmitsmay be deterministic. In an example, Category 3 (for example, LBT withrandom back-off with a contention window of fixed size) may beimplemented. The LBT procedure may have the following procedure as oneof its components. The transmitting entity may draw a random number Nwithin a contention window. The size of the contention window may bespecified by the minimum and maximum value of N. The size of thecontention window may be fixed. The random number N may be employed inthe LBT procedure to determine the duration of time that the channel issensed to be idle before the transmitting entity transmits on thechannel. In an example, Category 4 (for example, LBT with randomback-off with a contention window of variable size) may be implemented.The transmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by a minimumand maximum value of N. The transmitting entity may vary the size of thecontention window when drawing the random number N. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle before the transmitting entitytransmits on the channel.

LAA may employ uplink LBT at the UE. The UL LBT scheme may be differentfrom the DL LBT scheme (for example, by using different LBT mechanismsor parameters), since the LAA UL may be based on scheduled access whichaffects a UE's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme include, but are not limited to,multiplexing of multiple UEs in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. A UL transmission burst from aUE perspective may be a continuous transmission from a UE with notransmission immediately before or after from the same UE on the sameCC. In an example, a UL transmission burst may be defined from a UEperspective. In an example, a UL transmission burst may be defined froman eNB perspective. In an example, in case of an eNB operating DL+UL LAAover the same unlicensed carrier, DL transmission burst(s) and ULtransmission burst(s) on LAA may be scheduled in a TDM manner over thesame unlicensed carrier. For example, an instant in time may be part ofa DL transmission burst or an UL transmission burst.

In an example embodiment, in an unlicensed cell, a downlink burst may bestarted in a subframe. When an eNB accesses the channel, the eNB maytransmit for a duration of one or more subframes. The duration maydepend on a maximum configured burst duration in an eNB, the dataavailable for transmission, and/or eNB scheduling algorithm. FIG. 10shows an example downlink burst in an unlicensed (e.g. licensed assistedaccess) cell. The maximum configured burst duration in the exampleembodiment may be configured in the eNB. An eNB may transmit the maximumconfigured burst duration to a UE employing an RRC configurationmessage.

The wireless device may receive from a base station at least one message(for example, an RRC) comprising configuration parameters of a pluralityof cells. The plurality of cells may comprise at least one license celland at least one unlicensed (for example, an LAA cell). Theconfiguration parameters of a cell may, for example, compriseconfiguration parameters for physical channels, (for example, a ePDCCH,PDSCH, PUSCH, PUCCH and/or the like).

Frame structure type 3 may be applicable to an unlicensed (for example,LAA) secondary cell operation. In an example, frame structure type 3 maybe implemented with normal cyclic prefix only. A radio frame may beT_(f)=307200·T_(s)=10 ms long and may comprise 20 slots of lengthT_(slot)=15360·T_(s)=0.5 ms, numbered from 0 to 19. A subframe may bedefined as two consecutive slots where subframe i comprises of slots 2 iand 2 i+1. In an example, the 10 subframes within a radio frame may beavailable for downlink and/or uplink transmissions. Downlinktransmissions may occupy one or more consecutive subframes, startinganywhere within a subframe and ending with the last subframe eitherfully occupied or following one of the DwPTS durations in a 3GPP Framestructure 2 (TDD frame). When an LAA cell is configured for uplinktransmissions, frame structure 3 may be used for both uplink or downlinktransmission.

An eNB may transmit one or more RRC messages to a wireless device (UE).The one or more RRC messages may comprise configuration parameters of aplurality of cells comprising one or more licensed cells and/or one ormore unlicensed (for example, Licensed Assisted Access-LAA) cells. Theone or more RRC messages may comprise configuration parameters for oneor more unlicensed (for example, LAA) cells. An LAA cell may beconfigured for downlink and/or uplink transmissions.

In an example, the configuration parameters may comprise a firstconfiguration field having a value of N for an LAA cell. The parameter Nmay be RRC configurable. N may be a cell specific or a UE specific RRCparameter. For example, N (for example, 6, 8, 16) may indicate a maximumnumber of HARQ processes that may be configured for UL transmissions. Inan example, the RRC message may comprise an RNTI parameter for amulti-subframe DCI. In an example, one or more RRC messages may compriseconfiguration parameters of multi-subframe allocation parameters,maximum number of HARQ processes in the uplink, and/or other parametersassociated with an LAA cell.

In an example, a UE may receive a downlink control information (DCI)indicating uplink resources (resource blocks for uplink grant) foruplink transmissions.

In an example embodiment, persistent (also called burst ormulti-subframe) scheduling may be implemented. An eNB may scheduleuplink transmissions by self scheduling and/or cross scheduling. In anexample, an eNB may use UE C-RNTI for transmitting DCIs formulti-subframe grants. A UE may receive a multi-subframe DCI indicatinguplink resources (resource blocks for uplink grant) for more than oneconsecutive uplink subframes (a burst), for example m subframes. In anexample, a UE may transmit m subpackets (transport blocks-TBs), inresponse to the DCI grant. FIG. 11 shows an example multi-subframegrant, LBT process, and multi-subframe transmission.

In an example embodiment, an uplink DCI may comprise one or more fieldsincluding uplink RBs, a power control command, an MCS, the number ofconsecutive subframes (m), and/or other parameters for the uplink grant.FIG. 15 shows example fields of a multi-subframe DCI grant.

In an example, a multi-subframe DCI may comprise one or more parametersindicating that a DCI grant is a multi-subframe grant. A field in amulti-subframe DCI may indicate the number of scheduled consecutivesubframes (m). For example, a DCI for an uplink grant on an LAA cell maycomprise a 3-bit field. The value indicated by the 3-bit field mayindicate the number of subframes associated with the uplink DCI grant(other examples may comprise, for example, a 1-bit field or a 2-bitfield). For example, a value 000 may indicate a dynamic grant for onesubframe. For example, a field value 011 may indicate a DCI indicatinguplink resources for 4 scheduled subframes (m=field value in binary+1).In an example, RRC configuration parameters may comprise a firstconfiguration field having a value of N for an LAA cell. In an exampleimplementation, the field value may be configured to be less than N. Forexample, N may be configured as 2, and a maximum number of scheduledsubframes in a multi-subframe grant may be 2. In an example, N may beconfigured as 4 and a maximum number of scheduled subframes in amulti-subframe grant may be 4. In an example, N may be a number ofconfigured HARQ processes in an UL. Successive subframes on a carriermay be allocated to a UE when the UE receives a multi-subframe UL DCIgrant from an eNB.

At least one field included in a multi-subframe DCI may determinetransmission parameters and resource blocks used across m consecutivesubframes for transmission of one or more TBs. The DCI may comprise anassignment of a plurality of resource blocks for uplink transmissions.The UE may use the RBs indicated in the DCI across m subframes. The sameresource blocks may be allocated to the UE in m subframes as shown inFIG. 11.

Asynchronous UL HARQ may be employed for UL HARQ operation(s). An uplinkDCI grant may comprise a HARQ process number (HARQ ID). The uplink DCImay further comprise at least one redundancy version (RV) and/or atleast one new data indicator (NDI). At least one new transmission and/orat least one retransmission may be scheduled by PDCCH DCI in LAA uplinkHARQ transmissions. Example embodiments may comprise processes forgranting resources calculating HARQ IDs and transmission parameters forone or more first TBs of HARQ Process(es). Example HARQ Processes fortransmission of TBs in multi-subframe bursts is shown in FIG. 14.

A UE may perform listen before talk (LBT) before transmitting uplinksignals. The UE may perform an LBT procedure indicating that a channelis clear for a starting subframe of the one or more consecutive uplinksubframes. The UE may not perform a transmission at the startingsubframe if the LBT procedure indicates that the channel is not clearfor the starting subframe.

A TB transmission may be associated with a HARQ process. Multiple HARQprocesses may be associated with TB transmissions in multiple subframes,for example, subframes n, n+1, n+2, . . . , n+m−1.

A field in the multi-subframe DCI may indicate the number of subframes(m) associated with the uplink grant. For example, a multi-subframe DCIfor an uplink grant on an LAA cell may comprise a 3-bit field, where avalue indicated by the 3 bits may indicate the number of subframesassociated with the grant (m=field value in binary+1). The DCI mayfurther comprise a HARD process number (HARQ ID: h). In an example, whenthe HARQ ID in the DCI grant indicates HARQ process ID=h and the 3-bitfield (m) is “000,” the DCI may indicate a dynamic grant for onesubframe and for HARQ ID=h. In an example, when HARQ ID=h and m is “011”(m=4), the DCI may indicate that the grant is also valid for subframesn+1, n+2 and n+3 for HARQ processes (h+1) Mod N, (h+2) Mod N and (h+3)Mod N, respectively. N may be a preconfigured number, for example, N=8or 16. Mod is a modulo function. For example, N may be a number ofconfigured HARQ processes. For example, when m=4, and h=3, and N=16,then HARQ process IDs may be 3, 4, 5, and 6, respectively for subframesn, n+1, n+2, and n+3, where the multi-subframe grant is associated withsubframes n, n+1, n+2, and n+3.

In an example for m=3, and HARQ ID=h. HARQ ID for subframes n, n+1, andn+2 may be h mod N, (h+1) mod N, and (h+2) mod N. For example when h=1,and N=8, then h mod N=h=1, (h+1) mod N=h+1=2, and (h+2) mod N=h+2=3.

The UE may apply a multi-subframe grant to m HARQ processes. HARQprocess ID may be incremented and rounded to modulo N: (HARQ_ID+i)modulo N. A first HARQ ID for a first subframe i in a multi-subframeburst may be calculated as: (the HARQ ID plus i) modulo a firstpre-configured number. The parameter i may indicate a subframe positionof the first subframe in the one or more consecutive uplink subframes.The parameter i may have a value of zero for a starting subframe. Theparameter i may have a value of the number minus one (m−1) for an endingsubframe. In an example, N may be a preconfigured number.

A DCI grant may comprise at least one redundancy version (RV), and atleast one new data indicator (NDI). In an example, multi-subframeresource allocation may be applicable to uplink grants for a first TB(for example, first transmission) of one or more HARQ process.

In an example, for a LAA SCell, and transmission mode 1, there may be 16uplink HARQ processes. For a LAA SCell, and transmission mode 2, theremay be 32 uplink HARQ processes. In an example embodiment, for a servingcell that is an LAA SCell, a UE may upon detection of an PDCCH/EPDCCHwith a multi-subframe uplink DCI grant for subframes starting subframen, may perform a corresponding PUSCH transmission, conditioned on asuccessful LBT procedure, in subframe(s) n+i with i=0, 1, . . . , m−1according to the PDCCH/EPDCCH and HARQ process ID mod (n_(HARQ_ID)+i,N_(HARQ)). Mod may be a module function. The value of m may bedetermined by the number of scheduled subframes field in thecorresponding multi-subframe grant DCI format. The UE may be configuredwith a maximum value of m by an RRC parameter in the at least one RRCmessage. The value of n_(HARQ_ID) may be determined by the HARQ processnumber field in the corresponding multi-subframe uplink DCI format. Inan example, N_(HARQ) may be 16.

An example embodiment for calculating HARQ ID(s) may reduce the DCI sizeand reduce downlink control overhead. Instead of transmitting multipleHARQ IDs for multiple subframes, one HARQ ID may be included in the DCIfor multiple subframes. Example embodiments provide a simple andefficient mechanism for calculating a HARQ ID for each subframe in amulti-subframe grant, when HARQ ID has an upper limit. Exampleembodiments may increase spectral efficiency, reduce downlink controloverhead, and simplify UE processing related to HARQ processes.

In an example, one or more HARQ re-transmissions (if any) may bedynamically scheduled by the eNB employing uplink grant DCIs for one ormore retransmissions. In an example embodiment, dynamic scheduling maybe implemented. A UE may transmit in a subframe on a carrier if itreceives an UL grant for that subframe.

In an example, when a UE receives a new UL DCI grant for a firsttransmission of one or more first TBs during applicability of a priorDCI grant (for example, multi-subframe DCI) on an LAA cell, the new DCIgrant may override the old one.

An example embodiment for DCI processing may enable an eNB to transmitupdated DCIs to over-ride previous DCIs when needed. This may enable aneNB and a UE to adjust and adapt to an updated scheduling in differentscenarios depending on link parameters, HARQ transmissions, and LBTsuccess or failure. This process may be employed to improve schedulingefficiency for an LAA cell.

In an example, a wireless device may receive, in a first subframe, afirst multi-subframe DCI indicating first uplink resources for the LAAcell. The first DCI being for a number of one or more consecutive uplinksubframes comprising a third subframe. The wireless device may receive,in a second subframe different from the first subframe, a second DCIindicating second uplink resources for the third subframe. In anexample, a new grant may override the old one. The wireless device maytransmit, via a plurality of resource blocks in the third subframe, oneor more transport blocks according to parameters of the most recentlyreceived first DCI or second DCI.

In an example embodiment, in order to transmit on the UL-SCH, the MACentity may have a valid uplink grant which it may receive dynamically onthe (E)PDCCH or in a Random Access Response. To perform requestedtransmissions, the MAC layer may receive HARQ information from lowerlayers. When the physical layer is configured for uplink spatialmultiplexing, the MAC layer may receive up to two grants (one per HARQprocess) for the same TTI from lower layers.

There may be one HARQ entity at a MAC entity for a Serving Cell with aconfigured uplink, which may maintain a number of parallel HARQprocesses allowing transmissions to take place continuously whilewaiting for the HARQ feedback on the successful or unsuccessfulreception of previous transmissions. The number of parallel HARQprocesses per HARQ entity may depend on UE capability(ies), for example,it may be 4, 6, 8, 16 or 32. In an example, when the physical layer isconfigured for uplink spatial multiplexing, there may be two HARQprocesses associated with a given TT, otherwise there may be one HARQprocess associated with a given TTI.

At a given TTI, if an uplink grant is indicated for the TTI, the HARQentity may identify the HARQ process(es) for which a transmission maytake place. The HARQ entity may route the received HARQ feedback(ACK/NACK information), MCS and resource, relayed by the physical layer,to appropriate HARQ process(es).

A HARQ process may be associated with a HARQ buffer. A HARQ process maymaintain a state variable CURRENT_TX_NB, which indicates the number oftransmissions that have taken place for the MAC PDU currently in thebuffer, and a state variable HARQ_FEEDBACK, which indicates the HARQfeedback for the MAC PDU currently in the buffer. When the HARQ processis established, CURRENT_TX_NB may be initialized to 0.

The sequence of redundancy versions may be 0, 2, 3, and/or 1. A variableCURRENT_IRV may comprise an index into the sequence of redundancyversions. In an example implementation, this variable may be an up-datedmodulo 4.

New transmissions may be performed on the resource and with the MCSindicated on (E)PDCCH or Random Access Response. Adaptiveretransmissions may be performed on the resource and, if provided, withthe MCS indicated on (E)PDCCH. Non-adaptive retransmission may beperformed on the same resource and with the same MCS as was used for thelast made transmission attempt.

An Uplink HARQ operation may be asynchronous for serving cells operatingaccording to Frame Structure Type 3 (for example, LAA cells).

In a non-adaptive UL HARQ process, the MAC entity may be configured witha Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQtransmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. Fortransmissions on HARQ processes and logical channels except fortransmission of a MAC PDU stored in the Msg3 buffer, the maximum numberof transmissions may be set to maxHARQ-Tx. For transmission of a MAC PDUstored in the Msg3 buffer, the maximum number of transmissions may beset to maxHARQ-Msg3Tx.

In an example embodiment, a MAC entity may perform the followingprocess. In a TI, the HARQ entity may: identify the HARQ process(es)associated with the TI, and for an identified HARQ process may performthe following process. If an uplink grant has been indicated for theprocess and the ITI: if the received grant was not addressed to aTemporary C-RNTI on (E)PDCCH and if the NDI provided in the associatedHARQ information has been toggled compared to the value in the previoustransmission of the HARQ process; or if the uplink grant was received on(E)PDCCH for the C-RNTI and the HARQ buffer of the identified process isempty; or if the uplink grant was received in a Random Access Response,the MAC may perform the following actions. If there is a MAC PDU in theMsg3 buffer and the uplink grant was received in a Random AccessResponse: obtain the MAC PDU to transmit from the Msg3 buffer. Else,obtain the MAC PDU to transmit from the “Multiplexing and assembly”entity; deliver the MAC PDU and the uplink grant and the HARQinformation to the identified HARQ process; and instruct the identifiedHARQ process to trigger a new transmission. Otherwise, the MAC mayperform the following: deliver the uplink grant and the HARQ information(redundancy version) to the identified HARQ process; and instruct theidentified HARQ process to generate an adaptive retransmission.

If an uplink grant has not been indicated for the process and the TI: ifthe HARQ buffer of this HARQ process is not empty: instruct theidentified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in theprevious transmission, the MAC entity may ignore NDI received in anuplink grant on (E)PDCCH for its Temporary C-RNTI. In an exampleembodiment, the above process may be for a licensed cell.

In an example embodiment, when the HARQ feedback is received for thisTB, the HARQ process in a MAC entity may: set HARQ_FEEDBACK to thereceived value.

If the HARQ entity requests a new transmission, the HARQ process mayperform: et CURRENT_TX_NB to 0; set CURRENT_IRV to 0; store the MAC PDUin the associated HARQ buffer; store the uplink grant received from theHARQ entity; set HARQ_FEEDBACK to NACK; and/or generate a transmissionas described below, and/or a combination of these tasks.

If the HARQ entity requests a retransmission, the HARQ process may:increment CURRENT_TX_NB by 1; if the HARQ entity requests an adaptiveretransmission: store the uplink grant received from the HARQ entity;set CURRENT_IRV to the index corresponding to the redundancy versionvalue provided in the HARQ information; set HARQ_FEEDBACK to NACK;generate a transmission as described below. Else, if the HARQ entityrequests a non-adaptive retransmission: if HARQ_FEEDBACK=NACK: generatea transmission as described below.

When receiving a HARQ ACK alone, the MAC entity may keep the data in theHARQ buffer. When no UL-SCH transmission can be made due to theoccurrence of a measurement gap, no HARQ feedback may be received and anon-adaptive retransmission may follow.

To generate a transmission, the HARQ process may: if the MAC PDU wasobtained from the Msg3 buffer; or if there is no measurement gap at thetime of the transmission and, in case of retransmission, theretransmission does not collide with a transmission for a MAC PDUobtained from the Msg3 buffer in the TI: instruct the physical layer togenerate a transmission according to the stored uplink grant with theredundancy version corresponding to the CURRENT_IRV value; incrementCURRENT_IRV by 1; and if there is a measurement gap at the time of theHARQ feedback reception for this transmission and if the MAC PDU was notobtained from the Msg3 buffer: set HARQ_FEEDBACK to ACK at the time ofthe HARQ feedback reception for the transmission.

After performing the above actions, when a HARQ maximum number oftransmissions is configured, the HARQ process may: ifCURRENT_TX_NB=maximum number of transmissions−1, flush the HARQ buffer.

An asynchronous HARQ may be implemented for UL HARQ for an unlicensedcell. The scheduler at the eNB may schedule UL transmissions andretransmissions. Transmissions or retransmissions may be scheduled via(E)PDCCH. Implementation of mechanisms implemented in legacy uplinksynchronous HARQ for unlicensed cells adopting an asynchronous HARQ mayresult in many issues. Example embodiments may enhance implementation ofasynchronous uplink HARQ.

In an example embodiment, a wireless device may receive one or moreradio resource control (RRC) messages comprising configurationparameters for a licensed assisted access (LAA) cell. The one or moreRRC messages may comprise one or more consecutive uplink subframeallocation configuration parameters. In an example, the one or moreconsecutive uplink subframe allocation configuration parameterscomprises a first field, N.

A wireless device may receive a downlink control information (DCI)indicating uplink resources in a number of one or more consecutiveuplink subframes of the LAA cell. The DCI may comprise: the number ofthe one or more consecutive uplink subframes (m); an assignment of aplurality of resource blocks; and a transmit power control command. Thefirst field may indicate an upper limit for the number of the one ormore consecutive uplink subframes.

The wireless device may perform a listen before talk procedureindicating that a channel is clear for a starting subframe of the one ormore consecutive uplink subframes. The wireless device may transmit oneor more transport blocks, via the plurality of resource blocks usedacross the one or more consecutive uplink subframes. At least one fieldincluded in a multi-subframe DCI may determine transmission parametersand resource blocks used across m consecutive subframes for transmissionof one or more TBs. The DCI may comprise an assignment of a plurality ofresource blocks for uplink transmissions. The UE may use the RBsindicated in the DCI across m subframes. The same resource blocks may beallocated to the UE in m subframes.

A transmission power of the one or more transport blocks in eachsubframe of the one or more consecutive uplink subframes may employ thetransmit power control (TPC) command in the multi-subframe DCI. Atransmission power of the one or more transport blocks in each subframeof the one or more consecutive uplink subframes may be adjusted in eachsubframe when a total transmit power in each subframe exceeds a powervalue in each subframe. The power value may be an allowed maximumtransmission power of the wireless device. A calculation of thetransmission power may employ a measured pathloss value. Thetransmission power the one or more transport blocks in each subframe ofthe one or more consecutive uplink subframes may employ the same closedloop adjustment factor (calculated employing, at least, the TPC inmulti-subframe DCI). The closed loop adjustment factor may be calculatedemploying the transmit power control command.

An UL grant for subframe n sent by an eNB, for example, on subframe n−4,may comprise a power control command from eNB for UE to adjust itsuplink transmission power for transmission of a signal, for example,PUSCH, SRS, etc on an uplink of an LAA SCell. A UE may calculate atransmit power considering a power control command received from theeNB. Enhanced power control mechanisms may be implemented for uplinktransmission when an eNB transmits a multi-subframe UL grant applicableto multiple subframes.

In an example embodiment, a UE may receive a multi-subframe uplink DCIgrant comprising a TPC for one or more consecutive subframes startingfrom subframe n. The UE may calculate uplink transmit power for subframen based on the TPC command and other power parameters as described inPUSCH/SRS power calculation mechanism. T his may be considered abaseline power for transmission on subframes associated with themulti-subframe uplink grant. The UE may apply the same baseline power tosubframes associated with the multi-subframe grant. For example, TPCcommand may be employed to calculate a closed loop adjustment factor(f(i)) for subframe i. The same closed loop adjustment factor may beemployed for subframes in the one or more consecutive subframesassociated with the multi-subframe uplink grant.

In an example, for subframe i in one or more consecutive subframes,f(n)=f(n−1)+TPC, when accumulation is enabled and where the TPC is thetransmit power control received in the multi-subframe grant. f(n) may becalculated for subframe n (the starting subframe in the one or moresubsequent subframes) and may be applied to all subframes in the one ormore consecutive subframes. This implies that f(n)=f(n−1)+TPC for thestarting subframe in the one or more consecutive subframes, andf(i)=f(i−1) for subsequent subframes, where i>n and subframe i is one ofthe subsequent subframes in the one or more consecutive subframes.

In an example, for subframe n in one or more consecutive subframes, f(n)may equal TPC when accumulation is not enabled and where the TPCcomprises the transmit power control received in the multi-subframegrant f(n) may be calculated for subframe n (the starting subframe inthe one or more subsequent subframes) and may be applied to allsubframes in the one or more consecutive subframes. This may imply thatf(i)=TPC for each subframe i in the one or more consecutive subframes.

An example embodiment for a multi-subframe grant may reduce downlinkcontrol overhead by including one TPC field and one RB resourceassignment field in a multi-subframe grant for multiple subframes.Example embodiments provide a flexible method for resource assignmentand power calculations for multiple subframes. An example embodiment mayreduce overhead control signaling for resource block assignment(s). Anexample embodiment reduces overhead control signaling for TPCtransmission while maintaining flexibility for each subframe powercalculation. Although one TPC field is transmitted in a multi-subframeDCI grant, power calculation(s) may be performed for each subframeseparately. A wireless device may have different transmit power valuesfor different subframes (of an LAA cell) associated with amultiple-subframe grant, while using the same TPC field. Calculating thesame power value for multiple subframes may introduce unnecessaryconstraints which may reduce uplink transmission efficiency in somescenarios. Example embodiments may reduce downlink control overheadwhile providing flexibility for separate transmit power calculations foreach subframe when needed.

The UE may adjust the UE signal transmit power when needed based onmaximum allowed transmit power limitation of a UE in a subframe. Forexample, if multi-subframe grant is applicable to subframes n, n+1 andn+2, a UE may calculate a baseline power for the uplink transmission ofPUSCH. In subframes n, n+1, and n+2, the UE may or may not adjust thetransmit power depending on power limitations in the subframe. The UEmay adjust (when needed) the transmit power in each subframe so that thetotal transmit power in each subframe is below a maximum allowedtransmit power of the UE in each subframe. In the example illustrated inFIG. 13A, LAA PUSCH may be adjusted differently in each subframe due topower limitations in subframes n, n+1, and n+2. When a calculated totalpower exceeds a threshold in a subframe, the UE may adjust PUSCHtransmit power in the subframe. The calculated power may be for licensedcell(s) and/or unlicensed cell(s). In the example illustrated in FIG.13B, the power may not be adjusted due to power limitations and pathlossis the same across subframes. The UE may maintain the same transmitpower for PUSCH transmission of the LAA cell across subframes.

In an example embodiment, a UE may calculate uplink transmit power forsubframe n based on a TPC command in the UL grant and other powerparameters as described in PUSCH power calculation mechanism. The UE maycalculate uplink transmit power on subframe n+1 based on TPC comment onUL grant and other power parameters as described in PUSCH powercalculation mechanism. The UE may employ the same closed loop adjustmentfactor (f(i)) as the baseline for all the subframes in the one or moresubsequent subframes.

The UE may apply adjustments, if needed, to compensate for changes inmeasured pathloss reference (for example, using a configured movingaverage equation, or based on a measured value). The transmit power maybe recalculated in a subframe when the pathloss has changed in thesubframe. The UE may also adjust the UE signal transmit power, ifneeded, based on a maximum allowed transmit power limitation of a UE ineach subframe. For example, if a multi-subframe grant is applicable forsubframes n, n+1 and n+2, a UE may calculate a baseline power for theuplink transmission of PUSCH. In subframes n, n+1, and n+2, the UE mayor may not adjust the transmit power depending on whether the pathlossreference measurement is changed. The UE may or may not adjust thetransmit power depending on power limitations in the subframe. The UEmay adjust (when needed) the transmit power in a subframe so that thetotal transmit power in a subframe is below a maximum allowed transmitpower of the UE in the subframe.

In an example embodiment, one or more RRC messages configuring the LAAcell may indicate whether a single baseline power is calculated forsubframes or whether each subframe may have its own calculated power(for example, based on pathloss reference value, etc). Power adjustmentsdue to UE maximum allowed power may be applicable to a subframe, whenneeded.

Uplink power control may control a transmit power of the differentuplink physical channels. In an example, the setting of the UE Transmitpower for a Physical Uplink Shared Channel (PUSCH) transmission may bedefined as follows. If the UE transmits PUSCH without a simultaneousPUCCH for the serving cell c, then the UE transmit power P_(PUSCH,c)(i)for PUSCH transmission in subframe i for the serving cell c may be givenby

${P_{{PUSCH},c}(i)} = {\min\begin{Bmatrix}{{P_{{CMAX},c}(i)},} \\{{10\mspace{11mu}{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}{\quad\lbrack{dBm}\rbrack}}$

If the UE transmits PUSCH simultaneous with PUCCH for the serving cellc, then the UE transmit power P_(PUSCH,c)(i) for the PUSCH transmissionin subframe i for the serving cell c may be given by

${P_{{PUSCH},c}(i)} = {\min\begin{Bmatrix}{{10\mspace{11mu}{\log_{10}\left( {{{\hat{P}}_{{CMAX},c}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)}},} \\{{10\mspace{11mu}{\log_{10}\left( {M_{{PUSCH},c}(i)} \right)}} + {P_{{O\_ PUSCH},c}(j)} + {{\alpha_{c}(j)} \cdot {PL}_{c}} + {\Delta_{{TF},c}(i)} + {f_{c}(i)}}\end{Bmatrix}{\quad\lbrack{dBm}\rbrack}}$

If the UE is not transmitting PUSCH for the serving cell c, for theaccumulation of TPC command received with DCI format 3/3A for PUSCH, theUE may assume that the UE transmit power P_(PUSCH,c)(i) for the PUSCHtransmission in subframe i for the serving cell c is computed byP _(PUSCH,c)(i)=min{P _(CMAX,c)(i),P _(O_PUSCH,c)(1)+α_(c)(1)·PL _(c) +f_(c)(i)} [dBm]where, P_(CMAX,c)(i) may be a configured UE transmit power in subframe ifor serving cell c and {circumflex over (P)}_(CMAX,c)(i) may be thelinear value of P_(CMAX,c)(i). {circumflex over (P)}_(PUCCH)(i) may bethe linear value of P_(PUCCH)(i). M_(PUSCH,c)(i) may be the bandwidth ofthe PUSCH resource assignment expressed in number of resource blocksvalid for subframe i and serving cell c. Further description of some ofthe parameters in a power control formula may be defined according tothe latest LTE-Advanced standard specifications (for example, 3GPP TS36.213). PL_(c) may be the downlink path loss estimate calculated in theUE for serving cell c in dB.

δ_(PUSCH,c) may be a correction value, also referred to as a TPC commandand may be included in PDCCH/EPDCCH with DCI format comprising acorresponding TPC. In an example, if the UE is configured with higherlayer parameter UplinkPowerControlDedicated-v12x0 for serving cell c andif subframe i belongs to uplink power control subframe set 2 asindicated by the higher layer parameter tpc-SubframeSet-r12, the currentPUSCH power control adjustment state for serving cell c is given byf_(c,2)(i), and the UE shall use f_(c,2)(i) instead of f_(c)(i) todetermine P_(PUSCH,c)(i). Otherwise, the current PUSCH power controladjustment state for serving cell c is given by f_(c)(i). f_(c,2)(i) andf_(c)(i) may be defined by the following example formulas.

f_(c)(i)=f_(c)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)) andf_(c,2)(i)=f_(c,2)(i−1)+δ_(PUSCH,c)(i−K_(PUSCH)) if accumulation isenabled based on the parameter Accumulation-enabled provided by higherlayers (for example, in RRC message). where δ_(PUSCH,c)(i−K_(PUSCH)) maybe signalled on PDCCH/EPDCCH with DCI format on subframe i−K_(PUSCH),and where f_(c)(0) is the first value after reset of accumulation. Forexample, the value of K_(PUSCH) is for FDD or FDD-TDD and serving cellframe structure type 1, K_(PUSCH)=4. For a serving cell with framestructure type 3, subframe i−K_(PUSCH) comprises the DCI comprising TPCfor subframe i, based on uplink grant format and grant timing.δ_(PUSCH,c)=0 dB for a subframe where no TPC command is decoded forserving cell c or where DRX occurs or i is not an uplink subframe in TDDor FDD-TDD and serving cell c frame structure type 2. In an example,δ_(PUSCH,c)=0 dB if the subframe i is not the starting subframescheduled by a PDCCH/EPDCCH of a multi-subframe uplink DCI grant. In anexample, if UE has reached P_(CMAX,c)(i) for serving cell c, positiveTPC commands for serving cell c shall not be accumulated. In an example,if a UE has reached minimum power, negative TPC commands shall not beaccumulated.

In an example embodiment, f_(c)(i)=δ_(PUSCH,c)(i−K_(PUSCH)) andf_(c,2)(i)=δ_(PUSCH,c)(i−K_(PUSCH)) if accumulation is not enabled forserving cell c based on the parameter Accumulation-enabled provided byhigher layers (for example, RRC layer). δ_(PUSCH,c)(i−K_(PUSCH)) is theTPC command received for subframe i.

In an example embodiment, if the UE is not configured with an SCG or aPUCCH-SCell, and if the total transmit power of the UE would exceed{circumflex over (P)}_(CMAX)(i), the UE may scale {circumflex over(P)}_(PUSCH,c)(i) for the serving cell c in subframe i such that thecondition

${\sum\limits_{c}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)}} \right)$is satisfied where {circumflex over (P)}_(PUCCH)(i) may be the linearvalue of P_(PUCCH)(i), {circumflex over (P)}_(PUCCH)(i) may be thelinear value of P_(PUSCH,c)(i), {circumflex over (P)}_(CMAX)(i) may bethe linear value of the UE total configured maximum output powerP_(CMAX) in subframe i and w(i) may be a scaling factor of {circumflexover (P)}_(PUSCH,c)(i) for serving cell c where 0≤w(i)≤1. In case thereis no PUCCH transmission in subframe i {circumflex over(P)}_(PUCCH)(i)=0.If the UE is not configured with an SCG or a PUCCH-Scell, and if the UEhas PUSCH transmission with UCI on serving cell j and PUSCH without UCIin any of the remaining serving cells, and the total transmit power ofthe UE would exceed {circumflex over (P)}_(CMAX)(i), the UE may scale{circumflex over (P)}_(PUSCH,c)(i) for the serving cells without UCI insubframe i such that the condition

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right)$is satisfied where {circumflex over (P)}_(PUSCH,j)(i) is the PUSCHtransmit power for the cell with UCI and w(i) is a scaling factor of{circumflex over (P)}_(PUSCH,c)(i) for serving cell c without UCI. Inthis case, no power scaling may be applied to {circumflex over(P)}_(PUSCH,j)(i) unless

${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} = 0$and the total transmit power of the UE still would exceed {circumflexover (P)}_(CMAX)(i).

For a UE not configured with a SCG or a PUCCH-SCell, note that w(i)values may be the same across serving cells when w(i)>0 but for certainserving cells w(i) may be zero. If the UE is not configured with an SCGor a PUCCH-SCell, and if the UE has simultaneous PUCCH and PUSCHtransmission with UCI on serving cell j and PUSCH transmission withoutUCI in any of the remaining serving cells, and the total transmit powerof the UE would exceed {circumflex over (P)}_(CMAX)(i), the UE mayobtain {circumflex over (P)}_(PUSCH,c)(i) according to

P̂_(PUSCH, j)(i) = min (P̂_(PUSCH, j)(i), (P̂_(CMAX)(i) − P̂_(PUCCH)(i)))  and${\sum\limits_{c \neq j}{{w(i)} \cdot {{\hat{P}}_{{PUSCH},c}(i)}}} \leq \left( {{{\hat{P}}_{CMAX}(i)} - {{\hat{P}}_{PUCCH}(i)} - {{\hat{P}}_{{PUSCH},j}(i)}} \right)$

In an example embodiment, if the UE is configured with a LAA SCell foruplink transmissions, the UE may compute the scaling factor w(i)assuming that the UE performs a PUSCH transmission on the LAA SCell insubframe i irrespective of whether the UE can access the LAA SCell forthe PUSCH transmission in subframe i according to the channel accessprocedures.

A DCI indicating a multi-subframe grant (MSFG) may be supported incarrier aggregation, for example, for an unlicensed cell (e.g. an LAAcell). Design of a multi-subframe grant (MSFG) may take into account thedesign of existing DCIs used for single subframe grants. For example,current LTE-A DCI Format 0 and 4 may be used for uplink grants with andwithout special multiplexing. DCI Format 0 and 4 may be updated tosupport MSFGs with or without special multiplexing.

A MSFG may allow a UE to transmit on multiple consecutive uplinksubframes based on some common set of transmission parameters. Some oftransmission parameters, like MCS level, power control command, and/orresource assignments (e.g. RBs) may be common across scheduledsubframes. Some parameters, like HARQ process ID, RV and/or NDI may besubframe specific. The DCI indicating a MSFG may comprise one or moreparameters indicating the number of consecutive subframes allowed fortransmission according to the grant. In an example, the parameters whichmay be configured by DCI may include the number of consecutive subframes(m) associated with the MSFG. A MSFG may provide resource allocation forsubframes starting from subframe n and ending at subframe n+m−1.

In an example, a MSFG DCI may include two parts. One or more fields of aMSFG DCI may be included in a dedicated DCI and one or more fields ofthe MSFG DCI may be included in a common DCI. The dedicated DCI may bereceived on a UE specific search space of a control channel ((e)PDCCH).In an example, the same common DCI that is employed for DL LAA dynamicsignaling (e.g. DCI including indication of partial/full end subframes)may also be employed for an uplink MSFG grant. An eNB may transmit thecommon DCI corresponding to a MSFG DCI on a common search space of PDCCHof the LAA cell.

There is a need to define UE behavior when an LBT for the startingsubframe of the one or more consecutive subframes associated with a MSFGis not successful. The UE may implement subsequent LBT attempts ifconfigured. There is a need to define data transmission mechanisms forwhen a UE's LBT is not successful for the starting subframe n in one ormore m consecutive subframes: subframe n to n+m−1.

When a UE receives a multi-subframe grant (MSFG) for UL transmissions ofm consecutive subframes on an LAA carrier, the UE may perform LBT beforetransmission on the scheduled subframes. A successful LBT may befollowed by a reservation signal if transmission of the reservationsignals is allowed and/or needed. The UE's LBT may or may not succeedbefore start of a first allowed transmission symbol of subframe n. In anexample, if UE's LBT is successful before a first allowed transmissionsymbol of subframe n, the UE may transmit data according tomulti-subframe DCI. The UE may transmit data (TBs) when LBT issuccessful.

The DCI indicating a MSFG may include parameters for UEs behavior due toLBT. A multi-subframe DCI may include possible LBT time interval(s)and/or at least one LBT configuration parameter. The DCI may indicateone or more configuration parameters for LBT process beforetransmissions corresponding to a MSFG.

In an example, one or more DCI may indicate configuration fortransmission of reservation signals, format of reservation signals,allowed starting symbol, and/or LBT intervals/symbols associated with aMSFG. For example, the DCI may indicate a PUSCH starting position in asubframe. LBT procedure may be performed before the PUSCH startingposition. One or more DCI may comprise configuration parametersindicating reservation signals and/or partial subframe configuration. Inan example embodiment, transmission of reservation signals and/orpartial subframe for a multi-subframe grant may not be supported.

In an example, a UE may perform LBT (e.g. in a symbol) before subframe nstarts. In an example, a UE may perform LBT in a first symbol ofsubframe n. A UE may be configured to perform LBT in one or more allowedsymbols of a subframe, or within a configured period/interval in asubframe. The multi-subframe grant DCI may include possible LBT timeinterval(s) and/or at least one LBT configuration parameter. Forexample, DCI may indicate that PUSCH starts in symbol 0 and a LBTprocedure is performed before PUSCH starts (e.g. last symbol of aprevious subframe). For example, DCI may indicate that PUSCH starts insymbol 1 and an LBT procedure is performed before PUSCH starts (e.g. insymbol 0).

In an example, one or more LBT configuration parameters may be indicatedin an RRC message. In an example, one or more RRC message configuring anLAA cell may comprise at least one field indicating an LBT interval.

In an example embodiment, when a UE's LBT does not succeed for atransmission opportunity in a scheduled starting subframe n, the UE mayperform LBT on the last symbol of subframe n or first symbol of subframen+1 (e.g. depending on LBT configuration parameter in the DCI), to checkif it can start transmission in subframe n+1. If the second LBT fails,the UE may repeat the LBT process for a next transmission opportunity.In an example, there may be one configured transmission opportunity persubframe. A UE may perform LBT process for m times and for m subframes.In an example, m may be signaled by an eNB through DCI in a MSFG. In anexample, an RRC message configuring the LAA cell may include at leastone LBT parameter. In an example, a multi-subframe DCI grant mayindicate LBT parameters (e.g. parameter m, LBT symbol/PUSCH startingposition) for MSFG.

FIG. 12 shows examples of MSFG and LBT processes when the number ofscheduled subframes is 4 (for subframes n, n+1, n+2, and n+3). The UEreceives MSFG and prepares packets (TBs) P1, P2, P3, and P4 fortransmission in subframes n, n+1, n+2, and n+3, respectively. The one ormore transport blocks prepared/stored for each subframe is associatedwith the HARQ process ID of the corresponding subframe.

In an example, if LBT succeeds for transmission on a subframe k>=nwithin scope of multi-subframe UL grant, the UE may transmit scheduleddata packets on a first available subframe/partial-subframe and mayfollow with transmission of subsequent packets (TBs) based on uplinkgrant till end of a scheduled period, e.g. subframe n+3. An example inwhich the first LBT attempt is successful is illustrated in FIG. 12,Example 1.

In an example, LBT process for subframes n and n+1 may fail and LBTprocess for subframe n+2 may succeed. The UE may transmit packets P3 andP4 originally scheduled for subframe n+2 and n+3. The UE may nottransmit packets P1 and P2 in subframes n and n+1 when LBT for subframesn and n+1 does not succeed. The UE may wait for eNB to reschedulepackets P1 and P2. The eNB may transmit subsequent uplink grants to theUE for transmission of P1 and P2. This example is illustrated in FIG.12, Example 2.

In an example, a wireless device may receive a DCI indicating uplinkresources in a set of m consecutive subframes 0 to m−1. The DCI maycomprise a first field indicating m; one or more second fieldsindicating one or more listen-before-talk (LBT) configurations. The DCImay further comprise a third field indicating timing information forperforming LBT for a subframe. The wireless device may store one or moretransport blocks corresponding to each subframe in the set of mconsecutive subframes. TB(s) corresponding to a subframe are transmittedin the subframe if channel is available during the subframe. If thechannel is not available in a subframe k, TB(s) corresponding to thesubframe n are stored but are not transmitted. The UE may perform LBTfor access to the channel in subframe k+1, and different TBs (differentfrom TBs not transmitted in subframe n) corresponding to subframe k+1are transmitted in subframe n+1, if the channel is available during thesubframe k+1.

The wireless device may perform an LBT procedure on a channel to make atransmission in subframe k+1 according to the one or more LBTconfigurations and the timing information, if the wireless device cannotaccess the channel for a transmission in subframe k, k∈{0, . . . , m−2}.The wireless device may transmit one or more transport blockscorresponding to subframe k+1, if the LBT procedure indicates a clearchannel. The wireless device has access to the channel in subframe k, ifLBT procedure succeeds in subframe k. The wireless device has access tothe channel in subframe k, if the wireless device makes a transmissionin subframe k.

Example embodiments provide a dynamic and efficient method for LBTprocedures when a MSFG is received. DCI associated with a MSFG enabledynamical control of LBT configuration and/or timing for a MSFG burst.The wireless device implements an LBT procedure and TB transmissionprocess according to the MSFG. The wireless device may attempt an LBTfor each subframe associated with MSFG until LBT is successful.Performing a limited number of LBT procedures in allowed configuredintervals for subframes according to the DCI provides a dynamic andefficient mechanism for LBT procedure that reduces UE processingrequirements and reduces UE power consumption. TBs are associated with agiven subframe, and associated TB(s) to a subframe are transmitted ifthe channel is clear for transmission in the subframe. This mechanismenables both UE and eNB to associate a TB to the HARQ processcorresponding the subframe. The eNB may not need to determine whether aTB is not received due to LBT failure or excessive interference. Exampleembodiments provide an improved process for LBT procedure and packettransmission when a MSFG is received from an eNB.

In an example embodiment, various configuration for transmission ofreservation signals (e.g. format of reservation signals, allowedstarting symbol, LBT intervals/symbols, etc). One or more RRC messagesmay comprise configuration parameters indicating reservation signalsand/or partial subframe configuration. One or more DCI may compriseconfiguration parameters indicating reservation signals and/or partialsubframe configuration. In an example embodiment, transmission ofreservation signals and/or partial subframe for a multi-subframe grantmay not be supported.

In an example, a UE may be configured to transmit a reservation signalto reserve the channel when LBT is successful. In an example, a UE maynot be configured to transmit a reservation signal to reserve thechannel when LBT is successful.

A UE behavior in terms of above examples may be pre-defined, may be RRCconfigurable or may be dynamically configured by the eNB through one ormore common or dedicated DCIs. Indication through DCI may provide an eNBwith flexibility in both DL and UL scheduling of subframes on LAAcarrier as it may dynamically control UE's use of uplink subframes givenunpredictable outcome of LBT.

In an example embodiment, in deployment scenarios where loading is lowor when presence of other technologies and/or uncoordinated LAA cellsmay be guaranteed common behavior may be expected for same UE acrossmultiple grants and even across multiple UE's in which case RRCsignaling may also be implemented.

The UE may consider COT limit and may stop transmission based onreaching COT limit. When an eNB provide a UE with a multi-subframegrant, the eNB may have information about the number of subframes the UEis allowed to transmit before it reaches its maximum channel occupancytime (COT). When an eNB schedules more subframes N than what UE isenable to transmit within its maximum COT, M, the UE may transmit one ormore subframes based on the grant and may stop when the UE reaches itsend of COT. The eNB may reschedule remaining scheduled but nottransmitted UL allocations.

An eNB may transmit to a UE one or more RRC message comprisingconfiguration parameters of a plurality of cells. The plurality of cellsmay comprise one or more licensed cell and one or more unlicensed (e.g.LAA) cells. The eNB may transmit one or more DCIs for one or morelicensed cells and one or more DCIs for unlicensed (e.g. LAA) cells toschedule downlink and/or uplink TB transmissions on licensed/LAA cells.

Uplink Hybrid-ARQ design for licensed carriers in LTE-A may besynchronous, e.g. uplink retransmissions may occur at a prioripre-determined subframe relative to the previous transmission. In thecase of FDD operation uplink retransmissions may occur eight subframesafter the prior transmission attempt for the same hybrid-ARQ process. Amode of operation for UL HARQ may be non-adaptive where the set ofresource blocks used for the retransmissions may be identical to theinitial transmission. A hybrid-ARQ acknowledgement is transmitted on thePHICH. When a negative acknowledgement is received on the PHICH, thedata is retransmitted with the same transmission parameters and resourceblocks as previous transmission.

In an example, uplink HARQ may allow adaptive re-transmissions, wherethe resource-block set and/or modulation-and-coding scheme forretransmissions may be changed by an eNB through uplink grants forretransmissions. While non-adaptive retransmissions may be used due to alower overhead, adaptive retransmissions may be useful to avoid orreduce fragmenting the uplink frequency resource or to avoid or reducecollisions with random-access resources.

In an example, for a licensed cell, DCI Format 0 and 4 may be used foruplink grants with and without special multiplexing, respectively. Theuplink DCI grant may include one or more of the following fields: Flagfor format0/format1A differentiation, Hopping flag, N_ULhop, Resourceblock assignment, MCS/RV, NDI (New Data Indicator), TPC for PUSCH,Cyclic shift for DM RS, UL index (TDD only), Downlink Assignment Index(DAI), CSI Request, SRS Request, and/or MIMO parameters, e.g. precodinginformation and/or the number of layers.

An eNB may transmit to a wireless device an uplink DCI grant. The uplinkDCI grant may comprise a new-data indicator (NDI). The wireless devicemay flush a transmission buffer when an NDI is included in the DCI foradaptive and/or non-adaptive hybrid ARQ. The new-data indicator istoggled to indicate a transmission for at least one new transport block.If the new-data indicator is toggled, the terminal may flush thetransmission buffer and transmit at least one new data packet (TB). Whenthe new-data indicator is not toggled the previous transport block maybe retransmitted with a requested redundancy version.

In a licensed cell, when a retransmission is scheduled by a DCItransmitted via a PDCCH, the eNB may indicate which redundancy version(RV) should be transmitted. In an example, uplink grants forretransmissions may use the same MCS format as the initial transmissionMCS format. The uplink DCI grant may include a field that combinesinformation on the RV indication and modulation-and-coding scheme (MCS).The uplink DCI grant may comprise an IMCS field (e.g. 5 bits) indicatingan MCS for an initial transmission with an RV=0 or a re-transmission RVof e.g. 1, 2 or 3. The TB retransmission may use the same MCS format asthe initial TB transmission (with RV=0) MCS format. In an example, thefive-bit IMCS field can have 32 different binary combination values. 29IMCS field values may be used to indicate MCS for an initialtransmission, e.g. with RV=0. The three remaining IMCS field values maybe used to indicate grants for RV=1, 2 and 3. The transport block sizefor RV=1, 2, 3 may be known from the initial transmission and may notchange between retransmission attempts. Configuring a single field forboth MCS and RV reduces the size of an uplink grant DCI. The reducedflexibility does not have a sizeable negative impact on a licensed celluplink transmission performance and may actually simplify the HARQencoding process. In an example, uplink DCI grant transmitted by an eNBmay not comprise the HARQ process ID.

In an LAA cell, uplink transmissions may follow an asynchronous HARQprocess. An eNB may schedule both transmissions and retransmissions.There may be no need for PHICH transmissions in the downlink. Uplinkgrants for LAA cells may provide a UE with parameters for asynchronousHARQ, and may include a HARQ process ID. In LAA cells, an eNB mayprovide UEs with uplink grants through self-scheduling or cross carrierscheduling.

In LAA SCells, an eNB may provide a UE with multi-subframe grants(MSFG). A multi-subframe grant (MSFG) may allow a UE to transmit onmultiple subframes (MSFG burst) based on a common set of transmissionparameters. Some of transmission parameters, like power control commandsand MCS may be common across scheduled subframes while some parameters,like HARQ process ID, RV and NDI may be subframe specific.

An uplink MSFG burst may include multiple TBs of multiple HARQprocesses. This may result in complexities in designing a MSFG DCI. AMSFG may include resource allocation information, MCS information, MIMOinformation, and/or HARQ related fields, along with other parameters.There is a need to provide an efficient design for DCI format forunlicensed cells, for example, MSFG DCI. The DCI format should provideflexibility for TB transmission of multiple HARQ processes, and shouldhave a reduced DCI size.

In an example embodiment, an MSFG DCI may include information about RV,NDI and HARQ process ID of a subframe of the grant. For example, when agrant is for m subframes, the grant may include at least m set of RVsand m set of NDIs for HARQ processes associated with m subframes in thegrant. In an example, subframe specific parameters may comprise one ormore of the following for each subframe of a MSFG burst: M bits for RV,example 2 bits for 4 redundancy versions; and/or 1 bit for NDI. Anexample of multiple uplink MSFG burst transmission and correspondingHARQ Process ID, RV, and NDI is shown in FIG. 14. In an example, atransport block may transmitted in multiple bursts with different RVsuntil the transport block is successfully decoded by the eNB. Each MSFGburst may have its own MCS indicated by a MSFG DCI. HARQ processidentifier associated with a subframe may be incremented in subsequentsubframes of a MSFG burst, for example, a burst with three subframes maybe associated with HARQ process identifiers 1, 2, and 3.

In an example, a MSFG DCI grant may comprise common parameterscomprising: TPC for PUSCH, Cyclic shift for DM RS, resource blockassignment, MCS and/or spatial multiplexing parameters (if any, forexample included in DCI format 4), LBT related parameters applied to theuplink burst, and/or Other parameters, e.g. one or more multi-subframeconfiguration parameters. These parameters may be the same for differentsubframes of a MSFG burst. Resource block assignment, MCS and/or spatialmultiplexing parameters may change from one MSFG burst to another MSFGburst. An uplink MSFG DCI may further include, for example, a CSI (e.g.aperiodic) request and/or an SRS (e.g. aperiodic) Request.

In an example, different TBs transmitted with different RV values for aHARQ process may have different sizes. A first TB transmitted with RV=0associated with a HARQ process may have resource block assignments, MCSand/or spatial multiplexing parameters of a first burst, a second TBtransmitted with RV=1 associated with the same HARQ process may have asecond resource block assignments, MCS and/or spatial multiplexingparameters of a second burst. Encoder in a transmitter may consider thisinto account when encoding the data to prepare different TBs fortransmission to the eNB. Different HARQ TBs (e.g. with RV=0, 1, 2, . . .) associated with a HARQ process may have different RB assignments, MCS,and MIMO parameters. There is a need to enhance DCI format for an LAAcell. The eNB may transmit to a UE an uplink DCI grant indicating uplinkresources for an LAA cell. The DCI may comprise an MCS field (e.g. 5bits) and at least one RV field (e.g. 2 bits).

In an example, an uplink DCI may employ 5 bit MCS field. The MCS fieldis encoded similar to I_MCS field for used in DCI format 0 and isinterpreted the same was to decode the MCS level. The same MCS may beapplied to multiple subframes of a MSFG burst. The DCI may use aseparate 2 bit RV for each subframe associated with the MSFG. ExampleDCI fields for a licensed cell and unlicensed cell (e.g. LAA cell) isshown in FIG. 16.

Example embodiment, enhances DCI format for an LAA cell compared with aDCI for a licensed cell. Combining MCS and RV field in a DCI for alicensed cell reduces DCI size and downlink overhead while having no orminimal impact in uplink radio efficiency. Separating MCS and RV fieldfor a DCI for an LAA cell provides additional flexibility needed formanaging packet retransmissions in an LAA cell as described in the aboveparagraphs. In additional it reduces the grant size specially when MSFGis considered. MCS field is common for the subframes associated with aMSFG, but DCI includes m RV field, one for each subframe associated withthe MSFG. The enhanced DCI format for an unlicensed (e.g. LAA) cellcomprise a separate MCS field and RV fields and provides enhancedflexibility for scheduling, e.g., MSFG bursts on the LAA cell.

In an example embodiment, a wireless device receives a first DCIindicating first uplink resources of a licensed cell. The first DCI maycomprise a first field indicating one of: an MCS for an initialtransmission with a RV value of zero; or a re-transmission RV value(e.g. 1, 2, 3). The wireless device may receive a second DCI indicatingsecond uplink resources of an LAA cell. The second DCI may comprise anMCS field and an RV field. The wireless device may transmit one or morefirst transport blocks (TBs) employing the first field to determine afirst MCS and a first RV for the one or more first TBs. The wirelessdevice may transmit one or more second TBs employing the MCS field todetermine a second MCS and the RV field to determine a second RV valuefor the one or more second TBs.

In an example embodiment, the common and subframe specific parametersare identified and signaled to UEs. In one example, common and subframespecific parameters of MSFG are included in the same DCI. In an example,a new DCI format is defined to include both common transmissionparameters and subframe specific parameters for multi-subframes and HARQprocesses.

In an example, common parameters and subframe specific parameters may betransmitted in separate DCIs. A UE receiving a multi-subframe grant mayreceive one DCI including common parameters applicable to an uplinkburst across subframes and a second DCI which may show HARQ parametersfor each subframe. For example, a first RNTI may be employed forsearching/decoding a common DCI and a second RNTI may be employed forsearching/decoding a subframe specific DCI. In an example, RNTI forcommon DCI may be pre-specified, or may be configured by a RRC messagecomprising the RNTI. In an example, common DCI may be transmitted oncommon search space of the LAA Cell. In an example, RNTI for subframespecific DCI may be configured for a UE using MAC/RRC signaling. In anexample, common parameters may be configured and transmitted through RRCSignaling and subframe specific parameters may be transmitted in a DCI.

A UE may receive at least one downlink control information (DCI) from aneNB indicating uplink resources in m subframes of a licensed assistedaccess (LAA) cell. In an example embodiment, an MSFG DCI may includeinformation about RV, NDI and HARQ process ID of a subframe of thegrant. For example, when a grant is for m subframes, the grant mayinclude at least m set of RVs and NDIs for HARQ processes associatedwith m subframes in the grant. In an example, subframe specificparameters may comprise one or more of the following for each subframeof a MSFG burst: M bits for RV, example 2 bits for 4 redundancyversions; and/or 1 bit for NDI.

In an example, common parameters may include: TPC for PUSCH, Cyclicshift for DM RS, resource block assignment, MCS and/or spatialmultiplexing parameters (if any, for example included in DCI format 4),LBT related parameters applied to the uplink burst, and/or Otherparameters, e.g. one or more multi-subframe configuration parameters.The MSFG DCI may comprise an RB assignment field, an MCS field, an TPCfield, an LBT field applicable to all the subframes associated with aMSFG. These parameters may be the same for different subframes of a MSFGburst Resource block assignment, MCS and/or spatial multiplexingparameters may change from one MSFG burst to another MSFG burst.

In an example, a UE may perform an LBT procedure for transmission in them subframes employing at least one LBT field in the MSFG DCI. The atleast one LBT field may indicate at least one LBT configurationparameter, e.g., LBT type/category, LBT symbol and/or LBT priorityclass. The UE may transmit, in each of the m subframes, one or moretransport blocks employing the RBs field and the MCS field across the msubframes and employing each RV field and each NDI field correspondingto each subframe in the m subframes. The transmission power of each ofthe one or more transport blocks in each subframe in the m subframes mayemploy a same closed loop adjustment factor and the TPC field. Thetransmission power of each of the one or more transport blocks in eachsubframe in the m subframes may be adjusted in each subframe when atotal calculated transmit power for each subframe exceeds a power valuein each subframe.

An UL grant for subframe n sent by an eNB, e.g. on subframe n−4, mayinclude a power control command from eNB for UE to adjust its uplinktransmission power for transmission of a signal, e.g. PUSCH, SRS, etc onan uplink of an LAA SCell. A UE may calculate a transmit powerconsidering a power control command received from the eNB. Enhancedpower control mechanisms may be implemented for uplink transmission whenan eNB transmits a multi-subframe UL grant applicable to multiplesubframes.

In an example embodiment, a UE may calculate uplink transmit power forsubframe n based on a TPC command in the UL grant and other powerparameters as described in PUSCH power calculation mechanism. The sameTPC command and closed loop adjustment factor may be considered fordifferent subframes of a MSFG burst. The UE may calculate uplinktransmit power on subframes of a burst based on a common TPC command onUL grant and other power parameters as described in PUSCH powercalculation mechanism. The UE may apply adjustments when needed tocompensate for changes in measured pathloss reference (e.g. using aconfigured moving average equation, or based on a measured value). Thetransmit power may be calculated for a subframe considering a pathlosschanged in a subframe. The UE may consider MCS, MIMO parameters, and/RBassignments for a given subframe for calculation of power for thesubframe in a burst. The UE may also adjust the UE signal transmit powerif needed based on maximum allowed transmit power limitations of a UE ina subframe. In addition, a UE may or may not adjust the transmit powerdepending on power limitations in the subframe. The UE may adjust (whenneeded) the transmit power in a subframe so that the total transmitpower in a subframe is below a maximum allowed transmit power of the UEin the subframe. Two examples are shown in FIG. 13A and FIG. 13B.Example embodiment reduces the size of the DCI, enhances powercalculations for uplink transmissions in a MSFG burst and/or enablessubframe by subframe power adjustments when a MSFG burst is transmitted.

In an example embodiment, one or more RRC messages configuring the LAAcell may indicate whether a single baseline power is calculated forsubframes or each subframe may have its own calculated power (e.g. basedon pathloss reference value, etc). Power adjustments due to UE maximumallowed power may be applicable to a subframe, when needed.

According to various embodiments, a device such as, for example, awireless device, a base station and/or the like, may comprise one ormore processors and memory. The memory may store instructions that, whenexecuted by the one or more processors, cause the device to perform aseries of actions. Embodiments of example actions are illustrated in theaccompanying figures and specification.

FIG. 17 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1710, a wireless device may receive a firstdownlink control information (DCI) indicating first uplink resources ofa licensed cell. The first DCI may comprise a first field indicating oneof: a modulation and coding scheme (MCS) for an initial transmissionwith a redundancy version of zero, or a re-transmission redundancyversion (RV) value. A second DCI indicating second uplink resources of alicensed-assisted-access cell may be received at 1720. The second DCImay comprise an MCS field and an RV field. At 1730, the wireless devicemay transmit one or more first transport blocks (TBs) employing thefirst field to determine a first MCS and a first RV value for the one ormore first TBs. At 1740, the wireless device may transmit one or moresecond TBs employing the MCS field to determine a second MCS and the RVfield to determine a second RV value for the one or more second TBs.

According to an embodiment, the first field may be encoded by five bits,the MCS field may be encoded by five bits, a table may be employed todetermine the first MCS using the first field, and the table may beemployed to determine the second MCS using the second MCS field. There-transmission RV may, for example, have one of the following values:one, two or three. The RV field may, for example, have one of thefollowing values: zero, one, two, or three. According to an embodiment,the first DCI may not comprise a HARQ process ID, and the second DCI maycomprise a HARQ process ID. The second DCI may further comprise, forexample, a listen before talk (LBT) field employed for performing an LBTprocedure before transmitting the one or more second TBs. The second DCImay further comprise, for example, a resource blocks (RBs) fieldemployed for transmitting the one or more second TBs. The second DCI mayfurther comprise, for example, a new data indicators (NDI) fieldemployed for transmitting the one or more second TBs.

FIG. 18 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1810, a base station may transmit a firstdownlink control information (DCI) indicating first uplink resources ofa licensed cell. The first DCI may comprise a first field indicating oneof: a modulation and coding scheme (MCS) for an initial transmissionwith a redundancy version of zero, or a re-transmission redundancyversion (RV) value. A second DCI indicating second uplink resources of alicensed-assisted-access cell may be transmitted at 1820. The second DCImay comprise an MCS field and an RV field. At 1830, the base station mayreceive one or more first transport blocks (TBs) employing the firstfield to determine a first MCS and a first RV value for the one or morefirst TBs. At 1840, the base station may receive one or more second TBsemploying the MCS field to determine a second MCS and the RV field todetermine a second RV value for the one or more second TBs. According toan embodiment, the first field may be encoded is encoded by five bits,the MCS field may be encoded by five bits, a table may be employed todetermine the first MCS using the first field, and the table may beemployed to determine the second MCS using the second MCS field. There-transmission RV may, for example, have one of the following values:one, two or three. The RV field may, for example, have one of thefollowing values: zero, one, two, or three.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 1910, a wireless device may receive at leastone downlink control information (DCI) indicating uplink resources in aset of m consecutive subframes 0 to m−1. The at least one DCI maycomprise: a first field indicating m, one or more second fieldsindicating one or more listen-before-talk (LBT) configurations. The DCImay further comprise a third field indicating timing information forperforming an LBT procedure for a subframe. At 1920, the wireless devicemay store one or more transport blocks corresponding to each subframe inthe set of m consecutive subframes. At 1930, the wireless device mayperform the LBT procedure on a channel to make a transmission insubframe k+1 according to the one or more LBT configurations and thetiming information if the wireless device cannot access the channel fora transmission in subframe k, k∈{0, . . . , m−2}. At 1940, the wirelessdevice may transmit the one or more transport blocks corresponding tosubframe k+1 if the LBT procedure indicates a clear channel.

The wireless device may have access to the channel in subframe k if, forexample, the LBT procedure succeeds in subframe k. The wireless devicemay have access to the channel in subframe k if, for example, thewireless device makes a transmission in subframe k. According to anembodiment, the receiving the at least one DCI may comprise: receiving afirst DCI via a wireless device specific search space of a first controlchannel, and receiving a second DCI via a common search space of asecond control channel. The at least one DCI may indicate, for example:a modulation and coding scheme (MCS), a power control command, and aresource block assignment applicable to each subframe in the set of mconsecutive subframes. Each subframe in the set of m consecutivesubframes may be, for example, associated with a HARQ processidentifier, a redundancy version (RV) and a new data indicator (NDI).The one or more transport blocks stored for each subframe may be, forexample, associated with a HARQ process ID corresponding to thesubframe. The third field may indicate, for example, that the LBTprocedure for subframe k is performed in a first symbol of subframe k ora last symbol of subframe k−1. The at least one DCI may indicate, forexample, an allowed starting position for transmission in the subframe.The one or more LBT configurations may indicate, for example, at leastone of an LBT type or an LBT priority class.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2010, a wireless device may receive at leastone downlink control information (DCI) indicating uplink resources in aset of m consecutive subframes 0 to m−1. The at least one DCI maycomprise: a first field indicating m, one or more second fieldsindicating one or more listen-before-talk (LBT) configurations. The DCImay further comprise a third field indicating timing information forperforming an LBT procedure for a subframe. At 2020, the wireless devicemay perform the LBT procedure on a channel to make a transmission insubframe k+1. At 2030, the wireless device may sequentially, for k∈{1, .. . , m−1}, perform the LBT procedure on the channel to make atransmission in subframe k, if the wireless device cannot access thechannel for a transmission in subframe k−1. The LBT procedure may beperformed, for example, according to the one or more LBT configurationsand/or the timing information.

FIG. 21 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2110, a wireless device may receive at leastone DCI indicating uplink resources in a set of m consecutive subframes0 to m−1. The at least one DCI may comprise: a first field indicating w.The at least one DCI may further comprise a third field indicatingtiming information for performing a listen-before-talk (LBT) procedurefor a subframe. At 2120, the wireless device may perform the LBTprocedure on a channel to make a transmission in subframe k+1 if thewireless device cannot access the channel for a transmission in subframek, k∈{0, . . . , m−2}. The wireless device may perform the LBT procedureaccording to the timing information. At 2140, the wireless device maytransmit one or more transport blocks in subframe k+1 in response to theLBT procedure indicating a clear channel.

FIG. 22 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2210, a wireless device may receive at leastone DCI indicating uplink resources in a set of m consecutive subframes0 to m−1. At 2120, the wireless device may perform a LBT procedure on achannel to make a transmission in subframe k+1 if the wireless devicecannot access the channel for a transmission in subframe k, k∈{0, . . ., m−2}.

FIG. 23 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2310, a wireless device may receive a firstdownlink control information (DCI) indicating first uplink resources inm subframes of a licensed assisted access (LAA) cell. The at least oneDCI may comprise: a resource blocks (RBs) field, a modulation and codingscheme (MCS) field, a transmit power control (TPC) field, a listenbefore talk (LBT) field, a redundancy versions (RV) field for each ofthe m subframes, and a new data indicators (NDI) field for each of the msubframes. At 2320, the wireless device may perform an LBT procedure fortransmission in the m subframes employing the LBT field. At 2330, thewireless device may transmit, in each of the m subframes, one or moretransport blocks employing the RBs field and the MCS field across the msubframes and employing each RV field and each NDI field correspondingto each subframe in the m subframes. A transmission power of each of theone or more transport blocks in each subframe in the m subframes: mayemploy a same closed loop adjustment factor and the TPC field, and maybe adjusted in each subframe when a total calculated transmit power foreach subframe exceeds a power value in each subframe.

The transmission power of each of the one or more transport blocks maybe calculated for each subframe, for example, based on a pathloss valuefor each subframe. According to an embodiment, the receiving the atleast one DC may comprise: receiving a first DCI via a wireless devicespecific search space of a first control channel, and receiving a secondDCI via a common search space of a second control channel of the LAAcell. The at least one DCI may comprise, for example, a cyclic shiftfield applicable to the m subframes. The cyclic shift may be employedfor transmitting a demodulation reference signal. The at least one DCImay comprise, for example, a hybrid automatic repeat request (HARQ)identifier. A calculation of the transmission power may employ, forexample, a measured pathloss value. A calculation of the adjustmentfactor may employ, for example, a transmit power control command. TheLBT procedure may indicate, for example, that the channel is clear whena detected channel energy is below a threshold. Each subframe in the msubframe may be associated with, for example, a different HARQ processidentifier. The LBT field may indicate, for example, at least one LBTconfiguration parameter.

According to an embodiment, the at least one DCI may further comprise atransmit power control (TPC) field. The transmission power of each ofthe one or more transport blocks in each subframe in the m subframes:may, for example, employ a same closed loop adjustment factor and theTPC field; and be adjusted in each subframe when a total calculatedtransmit power for each subframe exceeds a power value in each subframe.

FIG. 24 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 2410, a base station may transmit a firstdownlink control information (DCI) indicating first uplink resources inm subframes of a licensed assisted access (LAA) cell. The at least oneDCI may comprise: a resource blocks (RBs) field, a modulation and codingscheme (MCS) field, a listen before talk (LBT) field, a redundancyversions (RV) field for each of the m subframes, and a new dataindicators (NDI) field for each of the m subframes. At 2420, the basestation may transmit, in each of the m subframes, one or more transportblocks employing the RBs field and the MCS field across the m subframesand employing each RV field and each NDI field corresponding to eachsubframe in the m subframes. According to an embodiment, an LBTprocedure performed by a wireless device for transmission in the msubframes employing the LBT field indicates a clear channel.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the disclosure may also be implemented ina system comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this disclosure may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, a first downlink control information (DCI) indicating firstuplink resources of a first subframe of a licensed cell, the first DCIcomprising a first field having a first number of bits indicating oneof: a modulation and coding scheme (MCS) for an initial transmissionwith a redundancy version of zero; or a re-transmission redundancyversion (RV) value; receiving a second DCI indicating second uplinkresources of a second subframe of a licensed-assisted-access cell, thesecond DCI comprising an MCS field having the first number of bits an RVfield having a second number of bits, and a transmit power control (TPC)field; transmitting, via the first subframe, one or more first transportblocks (TBs) employing the first field to determine a first MCS and afirst RV value for the one or more first TBs; and transmitting, via aphysical uplink shared channel during the second subframe, one or moresecond TBs employing the MCS field to determine a second MCS, the RVfield to determine a second RV value, and the TPC field to determine atransmit power value for the one or more second TBs.
 2. The method ofclaim 1, wherein: the first field is encoded by five bits; the MCS fieldis encoded by five bits; a table is employed to determine the first MCSusing the first field; and the table is employed to determine the secondMCS using the MCS field.
 3. The method of claim 1, wherein there-transmission RV value has one of the following values: one, two orthree.
 4. The method of claim 1, wherein the RV field has one of thefollowing values: zero, one, two, or three.
 5. The method of claim 1,wherein: the first DCI does not comprise a hybrid automatic repeatrequest (HARQ) process ID; and the second DCI comprises a HARQ processID.
 6. The method of claim 1, wherein the second DCI further comprises alisten before talk (LBT) field employed for performing an LBT procedurebefore transmitting the one or more second TBs.
 7. The method of claim1, wherein the second DCI further comprises a resource blocks (RBs)field employed for transmitting the one or more second TBs.
 8. Themethod of claim 1, wherein the second DCI further comprises a new dataindicators (NDI) field employed for transmitting the one or more secondTBs.
 9. A wireless device comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the wireless device to: receive a first downlink controlinformation (DCI) indicating first uplink resources of a first subframeof a licensed cell, the first DCI comprising a first field having afirst number of bits indicating one of: a modulation and coding scheme(MCS) for an initial transmission with a redundancy version of zero; ora re-transmission redundancy version (RV) value; receive a second DCIindicating second uplink resources of a second subframe of alicensed-assisted-access cell, the second DCI comprising an MCS fieldhaving the first number of bits an RV field having a second number ofbits, and a transmit power control (TPC) field; transmit, via the firstsubframe, one or more first transport blocks (TBs) employing the firstfield to determine a first MCS and a first RV value for the one or morefirst TBs; and transmit, via a physical uplink shared channel during thesecond subframe, one or more second TBs employing the MCS field todetermine a second MCS, the RV field to determine a second RV value, andthe TPC field to determine a transmit power value for the one or moresecond TBs.
 10. The wireless device of claim 9, wherein: the first fieldis encoded by five bits; and the MCS field is encoded by five bits; atable is employed to determine the first MCS using the first field; andthe table is employed to determine the second MCS using the MCS field.11. The wireless device of claim 9, wherein the re-transmission RV valuehas one of the following values: one, two or three.
 12. The wirelessdevice of claim 9, wherein the RV field has one of the following values:zero, one, two, or three.
 13. The wireless device of claim 9, wherein:the first DCI does not comprise a hybrid automatic repeat request (HARQ)process ID; and the second DCI comprises a HARQ process ID.
 14. Thewireless device of claim 9, wherein the second DCI further comprises alisten before talk (LBT) field employed for performing an LBT procedurebefore transmitting the one or more second TBs.
 15. The wireless deviceof claim 9, wherein the second DCI further comprises a resource blocks(RBs) field employed for transmitting the one or more second TBs. 16.The wireless device of claim 9, wherein the second DCI further comprisesa new data indicators (NDI) field employed for transmitting the one ormore second TB s.
 17. A method comprising: transmitting, by a basestation, a first downlink control information (DCI) indicating firstuplink resources of a first subframe of a licensed cell, the first DCIcomprising a first field having a first number of bits indicating oneof: a modulation and coding scheme (MCS) for an initial transmissionwith a redundancy version of zero; or a re-transmission redundancyversion (RV) value; transmitting a second DCI indicating second uplinkresources of a second subframe of a licensed-assisted-access cell, thesecond DCI comprising an MCS field having the first number of bits, anRV field having a second number of bits, and a transmit power control(TPC) field; receiving, via the first subframe, one or more firsttransport blocks (TBs) employing the first field to determine a firstMCS and a first RV value for the one or more first TBs; and receiving,via a physical uplink shared channel during the second subframe, one ormore second TBs employing the MCS field to determine a second MCS, theRV field to determine a second RV value, and the TPC field to determinea transmit power value for the one or more second TBs.
 18. The method ofclaim 17, wherein: the first field is encoded by five bits; and the MCSfield is encoded by five bits; a table is employed to determine thefirst MCS using the first field; and the table is employed to determinethe second MCS using the MCS field.
 19. The method of claim 17, whereinthe re-transmission RV value has one of the following values: one, twoor three.
 20. The method of claim 17, wherein the RV field has one ofthe following values: zero, one, two, or three.